Feature/es 876 combined acceleration#238
Conversation
…ration in filters
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## development #238 +/- ##
===============================================
+ Coverage 71.36% 71.93% +0.57%
===============================================
Files 35 35
Lines 3279 3428 +149
===============================================
+ Hits 2340 2466 +126
- Misses 939 962 +23 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…into feature/ES-876_combined_acceleration
…eTechnology/endaq-python into feature/ES-876_combined_acceleration
…into feature/ES-876_combined_acceleration
…into feature/ES-876_combined_acceleration
There was a problem hiding this comment.
Maybe I just have a mutant device, but using a 500g PR accel, get_accelerometer_info looks at the sensor name of "3255A PR Accelerometer", and assumes it is a 6000g device. I think we store a range value elsewhere, or it could be pulled from the displayName of "Acceleration X (500g)"
I just tested this on one device, it is entirely possible this has a weird manifest because that happens to my devices sometimes
|
@pscheidler We try to avoid string parsing, as I've been told that older products, as well as some of our suppliers / users have differences that would prevent it. |
Added
get_unfied_accelerationinendaq.ide.info, which performs performs calculations for a theoretically more accurate signal.Additionally, Signature of
endaq.calc.utils'sresamplewas updated for extra parameter, and extra methodalign_dataframesinendaq.calc.utilswas added.